Node / styrene-lab / polyrhythm.git rns://e35de29a61974cd952fde3fe9c8500d5/styrene-lab/polyrhythm.git

🗀 Files • ☸ Work (0) • 🖹 Commits (37) • ⑃ Branches (1) • ⌆ Tags (0) • ♥ Thanks (0)

• Pure Rust TD-50 mapping core exists, including reversible velocity curves for feel testing.

• The Rust TD-50 mapper has ALSA sequencer I/O and preserves the legacy client/port contract.

• T383838polyrhythm is the validated runtime authority for DRS DrumGizmo start/check/monitor routing on this host.

• Desktop audio recovery is explicit: T383838recover-audio handles PipeWire/WirePlumber, COSMIC audio UI state, and common media clients together.

T282828

Most commands are intentionally bounded: normal start/switch/monitor controls do not restart audio services, and graph inspection uses bounded snapshots instead of broad discovery. T383838recover-audio --execute is the explicit exception for incident recovery; it recovers PipeWire/WirePlumber, onboard analog defaults, COSMIC audio UI state, and configured media clients as one dependency chain.

• DRS is the only default kit path.

• Alternate kits are explicit diagnostics only.

• OBS routing is off by default.

• Do not probe broad PipeWire graphs as part of normal control flows.

• Do not restart PipeWire/WirePlumber as part of kit switching. Use T383838recover-audio for explicit incident recovery only.

• Block live monitor routing when OBS receives the onboard speaker monitor feed.

• Preserve the known TD-50 mapper client/port names when ALSA I/O is added:

• client: T383838TD50-DrumGizmo-Hihat-Mapper

• port: T383838out

• Keep live replacement opt-in until validated against the DRS DrumGizmo path.

Starting or stopping the TD-50/DrumGizmo stack can cause the physical speakers to

emit a sudden burst/blare as JACK/PipeWire routes are created, removed, or

reconnected. This is a known side effect of live audio graph churn on the current

rig, not evidence that broad PipeWire probing is occurring.

Near-term safety wrapper work should mute or clamp monitor-facing sources before

feedback-prone operations, then restore only the intended onboard monitor path.

Until that exists, keep playback paused and monitor volume conservative before

T383838polyrhythm start --execute, T383838polyrhythm stop, or kit switching.

The CLI now applies a first-pass monitor safety wrapper around live start/stop:

it drops the configured monitor sink to a low safety volume before graph churn

and restores the configured monitor volume afterward. This is a mitigation, not

a guarantee; keep external playback paused for live stack transitions.

Use these commands during PipeWire routing diagnostics. T383838quiet is non-destructive: it lowers the monitor sink without killing DrumGizmo or the mapper.

T282828

Current desired baseline is T383838engine-only: DrumGizmo running, mapper MIDI linked, and all DrumGizmo audio outputs disconnected. OBS receiving the onboard speaker monitor feed is flagged suspicious because it may participate in feedback loops; T383838monitor-test --execute now refuses live speaker routing while that OBS feedback hazard is present.

If desktop audio loses devices or media clients go silent after an audio-stack incident, do not keep restarting PipeWire by hand. Use the encoded recovery path:

T282828

On this COSMIC host, healthy T383838pactl/T383838wpctl output alone is not enough. The COSMIC panel/audio applet and surviving media clients can stay stale after a backend restart.